Release 10.1A: OpenEdge Deployment:
WebClient Applications

Preparing documentation for your end users

You must provide documentation for your users that includes following information:

The WebClient installer and the application installer can potentially make changes to system DLL files, therefore, in order to install and run a WebClient application over the Web, one of your end users must have Administrator privileges.
The end user’s machine must run either Netscape 4.x (or later) or Microsoft Internet Explorer 4.x (or later) to install WebClient and run the application.
You should inform users that during WebClient installation they must provide the proxy host and port of any firewall on their system. For more information, see the "WebClient Application Manager" section.
You should warn users that during the WebClient and application installation they might be told to reboot their machines after the WebClient and application are installed.
To run your application, users must have Web access. Even though the application is installed on a user’s machine, WebClient Initializer checks the application configuration file on your Web site each time the application is run to verify whether there is a new version of WebClient or the application.

If their browser displays an alert box similar to the one shown in Figure 8–1, users must choose the Open it option to install or start the application.



Figure 8–1: Sample browser file download alert box

Users can clear the Always ask before opening this type of file check box if they do not want to see this alert box the next time they launch the application from their browser.

Note: Clearing this check box turns off notification for all WebClient applications that the user launches from their browser.
If Netscape is running on a user’s machine when WebClient is installed and the user subsequently wants to use Netscape to start the application, the user must first stop and restart Netscape, and then start the application. Otherwise, when the file with the .prowcapc extension is automatically downloaded to the user’s machine, Netscape does not know the associated application (WebClient Initializer) to open the file and displays a dialog box prompting the user to specify the application. If users see this dialog box, they must shut down and restart Netscape to invoke the application.
When users first install WebClient from your Web site, the browser might require them to download a setup player for the installer. When they download the player, a dialog box prompts them to Grant a certificate that allows the player to be installed. You should advise your users that they must always choose to Grant the certificate.
You must tell users how to run the WebClient Application Manager to access the WebClient Initializer log file or make any post-installation changes to their application configuration. For more information see the "WebClient Application Manager" section.
If you use IntelliStream to install your application, you must tell your end users that if they uninstall the WebClient application, they must first uninstall your application and then uninstall the WebClient itself.
If your application performs HTTPS connections to a Web server that uses digital certificates signed by a private CA, you must provide your end users with documentation about your installation package for digital certificates. Your documentation should direct the end user to first download and install the WebClient and then immediately install the root digital certificates. Your documentation should also provide your end users with detailed information about how they would update the root digital certificates for the WebClient. Because each public or private PKI vendor has different procedures for installing and using digital certificates, you need to provide explicit directions for each PKI vendor you use. For more information, see Chapter 5, " Designing Security."